Difference between revisions of "Los POJOs Survey"

From mn/ifi/inf5750
Jump to: navigation, search
Line 29: Line 29:
 
*The app should have a separate admin gui for specifying skip logic.
 
*The app should have a separate admin gui for specifying skip logic.
 
*The skip logic will be stored in "System settings" on dhis2 with a key comprising of LosPOJOs + formId.
 
*The skip logic will be stored in "System settings" on dhis2 with a key comprising of LosPOJOs + formId.
 +
*As there is no relationship in the dhis2 data-model between data elements and option sets, the app will not take option sets into consideration.
  
  
Line 37: Line 38:
  
 
=Milestones=
 
=Milestones=
 +
*Milestone 1: 1st November
 +
 +
Document features and architecture on Wiki
 +
 +
Show understanding of DHIS2 web apps
 +
 +
*Milestone 2: 15th November
 +
 +
First bare-bone version - static HTML
 +
 +
Uploadable as DHIS2 web app
 +
 +
*Milestone 3: 30th November
 +
*Finished, if applicable also with mobile app.
 +
*Final delivery: 8th December
 +
*Presentation: 9th December
  
 
=Individual tasks=
 
=Individual tasks=
  
 
=Suggested improvements to Web API=
 
=Suggested improvements to Web API=

Revision as of 15:03, 30 October 2013

Code

All code is hosted on GitHub: Our repo

The team

  • Marianne Grov (Git user: mgr090)
  • Øyvind Raasholm Tangen (Git user: oyvindrt)
  • Kristian Johannessen (Git user: kjohann)
  • Torkil Aamodt (Git user: tork)

Requirements

Technologies

Mandatory requirements

From the lecture slides

  • Single event data entry form.
  • Skip logic (eg. If pregnant, fill in these extra forms).
  • Make interface for easily defining form and skip logic (integrated with single event, but you’ll need some additional info).
  • Available as DHIS2 web app and Android app (phonegap).
  • Touch friendly UI.

Our own

  • The app should able to get form by input id from user.
  • The app should have a separate admin gui for specifying skip logic.
  • The skip logic will be stored in "System settings" on dhis2 with a key comprising of LosPOJOs + formId.
  • As there is no relationship in the dhis2 data-model between data elements and option sets, the app will not take option sets into consideration.


Optional requirements

  • The app should able to navigate a list of forms, where the app will get forms from /api/programStages.
  • The app should have a gui where a superuser can specify user roles that has access to specifying skip logic.
    • user roles will be stored using "System settings" with key LosPOJOs

Milestones

  • Milestone 1: 1st November

Document features and architecture on Wiki

Show understanding of DHIS2 web apps

  • Milestone 2: 15th November

First bare-bone version - static HTML

Uploadable as DHIS2 web app

  • Milestone 3: 30th November
  • Finished, if applicable also with mobile app.
  • Final delivery: 8th December
  • Presentation: 9th December

Individual tasks

Suggested improvements to Web API