Difference between revisions of "Rocketscience"

From mn/ifi/inf5750
Jump to: navigation, search
m (Organizing the project (Tasks))
m
Line 49: Line 49:
  
 
== Organizing the project (Tasks) ==
 
== Organizing the project (Tasks) ==
<s>At the moment the team works mostly collaborative, until the main parts of the app is completed, and we can structure different tasks to different team members.</s>
+
We decided to work mostly using pair programming, and dividing simple tasks between us in trello when we saw it suitable.   
 
 
After Espen left the group, we decided to work mostly using pair programming, and dividing simple tasks between us in trello when we saw it suitable.   
 
  
 
== Screenshots and screen flows ==
 
== Screenshots and screen flows ==
Line 57: Line 55:
  
 
== Documented learning during project ==
 
== Documented learning during project ==
TODO
+
* We have gained knowledge of how DHIS2 web API works and how to create apps in the DHIS2 enviroment.
 +
* How to build a web application integrated with Angular, and how to structure a app with communicating with a web api
 +
* Map interaction
  
 
== Suggested improvements to APIs etc ==
 
== Suggested improvements to APIs etc ==
None as we've found the need for so far.  
+
Lat long coordinates are stored backwards in the database ([long,lat], instead of [lat,long]). We are not sure why, but it is not really a logical solution.
 +
 
 +
<nowiki> </nowiki>ImportConflicts from the server is in an unknown format (see under for example). Should probably be json? 
 +
 
 +
<span lang="EN-US">Validation Violation : {</span> 
 +
 
 +
<span lang="EN-US">                property = 'email', message = 'Not a valid email.', value = asdf@ asdf.asdf</span>
 +
 
 +
<span lang="EN-US">}</span>
  
 
== Download link to sample web app or Android app ==
 
== Download link to sample web app or Android app ==
 
TODO
 
TODO

Revision as of 14:16, 11 December 2015

Project: Managing organization units

Project Description and requirements

Web application for DHIS2 for managing organization units.

A user should be able to:

  • View and filter org. units
  • Get detailed information about a org. unit
  • Search org. units
  • CRUD org. units
    • Add a new facility location by map click

Technologies and Frameworks

  • Bootstrap
  • HTML5 & CSS3
  • AngularJS
  • DHIS2
  • Google Maps JavaScript API

List of group members

  1. Emil Døhlen Hansen (Emildh)
  2. Kristian Oddtrøen (Krisodd)
  3. Espen Hofsøy Stokkerud (espenhst) Dropped out

Schedule

Milestones

Milestone 1: 10th November

  • Document features and architecture on Wiki
  • Show understanding of DHIS2 web apps
  • Git repo

Milestone 2: 22th November

  • First bare-bone version - static HTML
  • Uploadable as DHIS2 web app

Milestone 3: 4th December

  • Finished

Milestone 4: 11th December

  • Final delivery

Milestone 5: Mid December

  • Presentation

Git Repository

Organizing the project (Tasks)

We decided to work mostly using pair programming, and dividing simple tasks between us in trello when we saw it suitable.

Screenshots and screen flows

TODO

Documented learning during project

  • We have gained knowledge of how DHIS2 web API works and how to create apps in the DHIS2 enviroment.
  • How to build a web application integrated with Angular, and how to structure a app with communicating with a web api
  • Map interaction

Suggested improvements to APIs etc

Lat long coordinates are stored backwards in the database ([long,lat], instead of [lat,long]). We are not sure why, but it is not really a logical solution.

ImportConflicts from the server is in an unknown format (see under for example). Should probably be json? 

Validation Violation : { 

                property = 'email', message = 'Not a valid email.', value = asdf@ asdf.asdf

}

Download link to sample web app or Android app

TODO