proposed data_model

user/
   LastCompletdDate was shortened to lastCompleted , by virtue of it being a long number it is pretty much a given it’s an epoch time. 
   created: username creation time
    role: From the user stories there seem to be 3 roles, “admin”, “taskadmin”, “contributor”
    completedTasks is now an array, which lists start / stop times
    The value here is we can grab all the users information and have it available in one request
    currentTasks similarly an array , a status is now added, either the task has been “taken” or it is in review. (The user cannot move things to the completedTasks blob, only the taskAdmin can do that). 

taskComments / 
    This json blob keeps track of all comments for a specific task. 
     Value here is we o’clocknly have to pull back the comments for the specific task we care about
     time is important, so you can display the comments chronologically. 

tasks/
   created time
   urls, to relevant content
   interests , which interest group to advertise to
   requirements, what are the requirements to run the specific test
   status , draft or published

interests / 
    list of all interests to present to the taskAdmin when creating a task
requirements
    list of all requirements to present to the taskAdmin when creating a task

(ideally the interests/ requirements can be search criteria as well )