Model

[pavelk2]

account

user properties (i used extra class profile for it, if there is a way - better to get rid of this extra class and to have properties directly connected to a user):

• short name
• full_name
• avatar_url

account

• user (many to many) - i think that we might need to have one user with several accounts, one account with many users - mostly for requestors. By default each user has 1 account.
• earnings
• spendings
• date_created
• balance (property)

fundtransfer

• from account
• to account
• currency (('VP','VIRTUAL POINTS'),('EU','EURO')) - as we draw on a piece of paper - there are 2 types of currency going around
• amount
• date_created
• description

jobs

app

• account (i think it is a cool idea to have apps connected to accounts, these accounts can group several users)
• user (just the one created the app)
• title
• token
• date_created

job

• app
• title
• description
• category (we might have many categories, currently - Espresso, Cappuccino, Wine, Volunteering)
• status (deleted, not published, published - if there are no any dataunits available - jobs is not published automatically)
• date_created
• userinterface_url (url - which refers to a raw html file with a UI template)
• userinterface_html (html code of the UI template taken from url mentioned above)
• webhook_url (this url called everytime new answer is submitted)
• gold_min
• gold_max
• score_min
• dataunits_per_task
• min_answers_per_dataunit
• max_dataunits_per_worker
• device_type (('MO','Mobile only'),('DO','Desktop Only'),('AD','Any device'))
• qualitycontrol_url

dataunit

• job
• value (JSON - would be great to store it separately in Mongo DB or similar)
• gold (true, false) - whether this dataunit is gold or not
• status (completed, not completed, deleted)
• date_created

answers

task

• job
• user (the worker completing this task)
• status (not completed, completed)
• date_created

answer (created automatically together with a task with empty value and score)

• task
• dataunit
• value (JSON - would be great to store it separately in Mongo DB or similar)
• score (integer value representing correctness 0 by default, negative or positive in case it is connected to gold data unit)